Added description of the behaviour of rename-restart.

Signed-off-by: Ewan Mellor <ewan@xensource.com>

diff --git a/docs/man/xmdomain.cfg.pod.5 b/docs/man/xmdomain.cfg.pod.5
index ad38ca09a2824d1ebc8b6e7df65dc2ed701a749b..313c3bc4b4b8d62820214a3f3fddc9065b55a090 100644 (file)
--- a/docs/man/xmdomain.cfg.pod.5
+++ b/docs/man/xmdomain.cfg.pod.5
@@ -120,8 +120,10 @@ real issue.
 =item I<rename-restart>
 
 The old domain will not be cleaned up, but will be renamed so a new
-domain can be restarted in it's place.  (TODO: what does this mean for
-resources?  What is the renamed name?)
+domain can be restarted in it's place.  The old domain will be renamed with
+a suffix -1, -2, etc, and assigned a new random UUID; the new domain will
+keep the original name and UUID.  The old domain will release the devices that
+it holds, so that the new one may take them.
 
 =back